Skip to content

Conversation

@laurilaatu
Copy link

A# Description

📝 Please include a summary of the change.

  • Please also include relevant motivation and context.
  • List any dependencies that are required for this change.

Type of change

For a new feature or function, please create an issue first to discuss it
with us before submitting a pull request.

Note: Please delete options that are not relevant.

  • Bug fix (non-breaking change that fixes an issue)
  • Documentation update
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • A new research paper code implementation
  • Other (Specify)

Tests

📝 Please describe the tests that you ran to verify your changes.

  • Provide instructions so we can reproduce.
  • Please also list any relevant details for your test configuration.

Test Configuration:

Checklist

  • I have read the guidelines for contributing.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have installed and run pre-commit on the files I edited or added.
  • I have added tests that prove my fix is effective or that my feature works.

jmitrevs and others added 30 commits February 7, 2024 10:24
JanFSchulte and others added 30 commits December 6, 2024 13:45
…fixes

Fixes to parsing of pytorch models when using torch functionals
…update-readme

Update README.md for v1.0.0
…ll_hook

Temporary workaround for QKeras installation
…fix_pointwise_res_type

Don't overwrite already set accum_t, fix pointwise output resolution
…tests

Split hgq tests and isolate qkeras tests to make tests run in under 1h
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants